docs: list externally-maintained extensions (pg_search/ParadeDB)#241
docs: list externally-maintained extensions (pg_search/ParadeDB)#241philippemnoel wants to merge 2 commits into
Conversation
Signed-off-by: Philippe Noël <philippemnoel@gmail.com>
Signed-off-by: Philippe Noël <philippemnoel@gmail.com>
9fe2e6f to
3eced36
Compare
|
We need to find a scalable solution for this problem, and I have a strong feeling that our current approach may not be the best option. I would like to gather input from other maintainers and carefully analyse vendor neutrality while ensuring quality for our users. |
Sounds good. We're happy to help in whatever way we can, thank you for considering the request. |
|
I conducted an initial assessment with some members of the PostgreSQL core and commit group. I understand that there isn't any available space for a project to operate under the |
Summary
Hi everyone. Philippe here from ParadeDB/pg_search. We are a PostgreSQL extension for full-text and vector search in Postgres. We are a commercial, open-source project and license under AGPL-3.0 to protect ourselves from AWS and other hyperscalers.
We opened #204, and following Gabriele's feedback we started publishing our own
cnpg-extensions-containersimage, to https://hub.docker.com/r/paradedb/paradedb-extension. I understand our license prohibits being listed in this repo, but I was wondering if the project was willing to document a list of externally-supported extension containers, like ours? This is a slightly self-interested request, in that it will help with our discoverability, but I also expect it could be beneficial for other such extensions (for instance, Timescale's non-permissive extension, or even closed-source ones from hyperscalers). What do you think?We used the build tooling from this repository. For context:
paradedb/paradedb-extension(e.g.paradedb/paradedb-extension:0.24.0-18-trixie)Happy to adjust the wording as well. Lmk and thank you!